Touch files after moving #158
Conversation
nilbus
changed the title
Codecov Report
@@ Coverage Diff @@
## master #158 +/- ##
=========================================
+ Coverage 57.03% 57.2% +0.16%
=========================================
Files 198 198
Lines 13055 13085 +30
=========================================
+ Hits 7446 7485 +39
+ Misses 4662 4655 -7
+ Partials 947 945 -2
Continue to review full report at Codecov.
|
|
Hey, thanks for sending this and for the feedback regarding the watching behavior. I'm glad to hear that there's a simple solution that's workable. I'm not sure why you're seeing a behavioral difference between
The first should be relatively easy to pick up. The latter would probably involve attaching I can have a look at this later this week. |
|
This is now tracked by #163. |
Problem overview: A project I use on a docker container watches for changes to files. It ignores file added and moved_to events, only listening file modification FS events to trigger the desired behavior (which never happens with Mutagen). Mutegen's staging strategy is a good and correct one; I'm just looking into the possibility of a workaround.
This is a spike to see if I could get something working, not ready to merge.
I'm confident that
Chtimesis running in my docker container, but unlike runningtouchlocally, it's not triggering modifications.I verified that the code in question is running by adding
os.Create(filePath = ".synced")adjacent to theChtimescall, and it does indeed create a.synced-suffixed file for each file that is modified.I'll continue investigating, including confirming whether Chtimes returns any error, but please let me know if you have any ideas that might put me in the right direction.